Delivery of content

ABSTRACT

Future data connection quality may be predicted based on past data connection quality, and future requests for data may be predicted based on past requests. These predictions may be used to help decide whether, when, and/or how to deliver the data in a proactive manner. For example, according to some aspects described herein, a future data connection quality may be predicted based at least on historical data connection quality. It may be determined whether to pre-deliver at least a first portion of an item of content based at least on the predicted future data connection quality. If so, then the at least the portion of the item of content may be pre-delivered to the device and/or to another destination.

BACKGROUND

In a network environment, data may be delivered to a device in responseto a request by the device. The data connection with the device may varyover time and under different conditions. For example, the networkitself may experience problems such as overloading, noise, and brokenconnections, or the device may have difficulty obtaining reliable signalstrength with the network. If the data connection happens to be poorduring data delivery, then delivery may suffer. This may be especiallyproblematic where the data is expected to be delivered in a consistentmanner, such as when the data represents streamed multimedia content.Data connection problems are typically handled using a reactive processin which the data quality may be reduced or delayed until the dataconnection improves. This type of reactive handling may sometimes resultin a poor end user experience. The foregoing and other shortcomings areaddress in this disclosure.

SUMMARY

The following summary is for illustrative purposes only, and is notintended to limit or constrain the detailed description.

In some aspects, rather than merely reacting to detected data deliveryissues while they are occurring, it may be desirable to predict futuredata connection quality based on past data connection quality. Futurerequests for data may also be predicted based on past requests. Thesepredictions may be used to help decide whether, when, and/or how todeliver the data in a proactive manner. For example, if it is predictedthat a future request for data may occur when it is likely that dataconnection quality will be poor, it may be desirable to pre-deliver atleast a portion of the data that is predicted to be requested. Or, wheredata is already being delivered, it may be desirable to pre-deliver afuture portion of the data if it is predicted that the future portionwill likely be sent during a time of poor data connection quality.

While some episodes of poor data connection quality may not always bepredictable, it has been found that there are factors that can affectdata connection quality that are predictable based on past dataconnection quality patterns. In one aspect, for example, if a networktypically experiences high usage at particular times of day and/orparticular days of the week, it may be predictable based on thisexperience that this pattern will likely continue in the future. Or, ifthe device to receive the data is a mobile device that is carried by theuser, the user may have a certain routine (e.g., commuting to work inthe morning, being at home in the evening, etc.) that results in arepeatable pattern of data connection quality.

According to some aspects as described herein, methods, apparatuses, andsoftware may perform, for example, at least the following process. Afuture point in time may be determined prior to a request (by, e.g., adevice) for an item of content. The future point in time may bedetermined based at least on information indicating a correlationbetween a past timeframe and data connection quality. Also prior to therequest, at least a first portion of the item of content may be sent(e.g., to the device and/or to another destination) beginning at thedetermined future point in time.

According to further aspects as described herein, methods, apparatuses,and software may perform, for example, at least the following process. Afuture data connection quality may be predicted based at least onhistorical data connection quality. It may be determined whether topre-deliver at least a first portion of an item of content to a devicebased at least on the predicted future data connection quality. If so,then at least the portion of the item of content may be pre-delivered(e.g., to the device and/or to another destination).

According to still further aspects as described herein, methods,apparatuses, and software may perform, for example, at least thefollowing process. A data connection quality may be predicted based atleast on historical data connection quality. It may be determinedwhether a current data connection quality is consistent with thepredicted data connection quality. It may further be determined whetherto send at least a portion of an item of content to a device using thepredicted data connection quality if the current data connection qualityis consistent with the predicted data connection quality. Or, if thecurrent data connection quality is inconsistent with the predicted dataconnection quality, then it may be determined whether to send at leastthe portion of the item of content to the device using the current dataconnection quality. In some aspects, if it is determined that the atleast the portion of the item of content should be sent, then the atleast the portion of the item of content is sent (e.g., to the deviceand/or to another destination).

As noted above, this summary is merely a summary of some of the featuresdescribed herein. It is not exhaustive, and it is not to be a limitationon the claims.

BRIEF DESCRIPTION OF THE DRAWINGS

These and other features, aspects, and advantages of the presentdisclosure will become better understood with regard to the followingdescription, claims, and drawings. The present disclosure is illustratedby way of example, and not limited by, the accompanying figures in whichlike numerals indicate similar elements.

FIG. 1 illustrates an example communication network on which variousfeatures described herein may be used.

FIG. 2 illustrates an example computing device that can be used toimplement any of the methods, servers, entities, and computing devicesdescribed herein.

FIG. 3 is a flow chart showing example steps that may be performed inaccordance with one or more aspects described herein.

FIGS. 4A-4C are graphs showing examples of predicted data connectionquality over time.

FIGS. 5A-5C are graphs showing further examples of predicted dataconnection quality over time.

FIG. 6 is another flow chart showing example steps that may be performedin accordance with one or more aspects described herein.

FIG. 7 is yet another flow chart showing example steps that may beperformed in accordance with one or more aspects described herein.

DETAILED DESCRIPTION

In the following description of various illustrative embodiments,reference is made to the accompanying drawings, which form a parthereof, and in which is shown, by way of illustration, variousembodiments in which aspects of the disclosure may be practiced. It isto be understood that other embodiments may be utilized, and structuraland functional modifications may be made, without departing from thescope of the present disclosure.

FIG. 1 illustrates an example communication network 100 on which many ofthe various features described herein may be implemented. Network 100may be any type of information distribution network, such as satellite,telephone, cellular, wireless, etc. One example may be an optical fibernetwork, a coaxial cable network, or a hybrid fiber/coax distributionnetwork. Such networks 100 use a series of interconnected communicationlinks 101 (e.g., coaxial cables, optical fibers, wireless, etc.) toconnect multiple premises 102 (e.g., businesses, homes, consumerdwellings, etc.) to a local office (e.g., q data processing facility, aheadend, etc.) 103. The local office 103 may transmit downstreaminformation signals onto the links 101, and each premises 102 may have areceiver used to receive and process those signals.

There may be one link 101 originating from the local office 103, and itmay be split a number of times to distribute the signal to variouspremises 102 in the vicinity (which may be many miles) of the localoffice 103. The links 101 may include components not illustrated, suchas splitters, filters, amplifiers, etc. to help convey the signalclearly, but in general each split introduces a bit of signaldegradation. Portions of the links 101 may also be implemented withfiber-optic cable, while other portions may be implemented with coaxialcable, other lines, or wireless communication paths.

The local office 103 may include an interface, such as a terminationsystem (TS) 104. More specifically, the interface 104 may be a cablemodem termination system (CMTS), which may be a computing deviceconfigured to manage communications between devices on the network oflinks 101 and backend devices such as servers 105-107 (to be discussedfurther below). The interface 104 may be as specified in a standard,such as the Data Over Cable Service Interface Specification (DOCSIS)standard, published by Cable Television Laboratories, Inc. (a.k.a.CableLabs), or it may be a similar or modified device instead. Theinterface 104 may be configured to place data on one or more downstreamfrequencies to be received by modems at the various premises 102, and toreceive upstream communications from those modems on one or moreupstream frequencies.

The local office 103 may also include one or more network interfaces108, which can permit the local office 103 to communicate with variousother external networks 109. These networks 109 may include, forexample, networks of Internet devices, telephone networks, cellulartelephone networks, fiber optic networks, local wireless networks (e.g.,WiMAX), satellite networks, and any other desired network, and thenetwork interface 108 may include the corresponding circuitry needed tocommunicate on the external networks 109, and to other devices on thenetwork such as a cellular telephone network and its corresponding cellphones.

As noted above, the local office 103 may include a variety of servers105-107 that may be configured to perform various functions. Forexample, the local office 103 may include a push notification server105. The push notification server 105 may generate push notifications todeliver data and/or commands to the various premises 102 in the network(or more specifically, to the devices in the premises 102 that areconfigured to detect such notifications). The local office 103 may alsoinclude a content server 106. The content server 106 may be one or morecomputing devices that are configured to provide content to users attheir premises. This content may be, for example, video on demandmovies, television programs, songs, text listings, etc. The contentserver 106 may include software to validate user identities andentitlements, to locate and retrieve requested content, to encrypt thecontent, and to initiate delivery (e.g., streaming) of the content tothe requesting user(s) and/or device(s).

The local office 103 may also include one or more application servers107. An application server 107 may be a computing device configured tooffer any desired service, and may run various languages and operatingsystems (e.g., servlets and JSP pages running on Tomcat/MySQL, OSX, BSD,Ubuntu, Redhat, HTML5, JavaScript, AJAX and COMET). For example, anapplication server may be responsible for collecting television programlistings information and generating a data download for electronicprogram guide listings. Another application server may be responsiblefor monitoring user viewing habits and collecting that information foruse in selecting advertisements. Yet another application server may beresponsible for formatting and inserting advertisements in a videostream being transmitted to the premises 102. Although shown separately,one of ordinary skill in the art will appreciate that the push server105, content server 106, and application server 107 may be combined.Further, here the push server 105, content server 106, and applicationserver 107 are shown generally, and it will be understood that they mayeach contain memory storing computer executable instructions to cause aprocessor to perform steps described herein and/or memory for storingdata.

An example premises 102 a, such as a home, may include an interface 120.The interface 120 can include any communication circuitry needed toallow a device to communicate on one or more links 101 with otherdevices in the network. For example, the interface 120 may include amodem 110, which may include transmitters and receivers used tocommunicate on the links 101 and with the local office 103. The modem110 may be, for example, a coaxial cable modem (for coaxial cable lines101), a fiber interface node (for fiber optic lines 101), twisted-pairtelephone modem, cellular telephone transceiver, satellite transceiver,local Wi-Fi router or access point, or any other desired modem device.Also, although only one modem is shown in FIG. 1, a plurality of modemsoperating in parallel may be implemented within the interface 120.Further, the interface 120 may include a gateway interface device 111.The modem 110 may be connected to, or be a part of, the gatewayinterface device 111. The gateway interface device 111 may be acomputing device that communicates with the modem(s) 110 to allow one ormore other devices in the premises 102 a, to communicate with the localoffice 103 and other devices beyond the local office 103. The gateway111 may be a set-top box (STB), digital video recorder (DVR), computerserver, or any other desired computing device. The gateway 111 may alsoinclude (not shown) local network interfaces to provide communicationsignals to requesting entities/devices in the premises 102 a, such asdisplay devices 112 (e.g., televisions), additional STBs 112, personalcomputers 114, laptop computers 115, wireless devices 116 (e.g.,wireless routers, wireless laptops, notebooks, tablets and netbooks,cordless phones (e.g., Digital Enhanced Cordless Telephone—DECT phones),mobile phones, mobile televisions, personal digital assistants (PDA),etc.), landline phones 117 (e.g. Voice over Internet Protocol—VoIPphones), and any other desired devices. Examples of the local networkinterfaces include Multimedia Over Coax Alliance (MoCA) interfaces,Ethernet interfaces, universal serial bus (USB) interfaces, wirelessinterfaces (e.g., IEEE 802.11, IEEE 802.15), analog twisted pairinterfaces, Bluetooth interfaces, and others.

FIG. 2 illustrates general hardware and/or software elements that can beused to implement any of the various computing devices discussed herein.The computing device 200 may include one or more processors 201, whichmay execute instructions of a computer program to perform any of thefeatures described herein. The instructions may be stored in any type ofcomputer-readable medium or memory, to configure the operation of theprocessor 201. For example, instructions may be stored in a read-onlymemory (ROM) 202, random access memory (RAM) 203, removable media 204,such as a Universal Serial Bus (USB) drive, compact disk (CD) or digitalversatile disk (DVD), floppy disk drive, or any other desired storagemedium. Instructions may also be stored in an attached (or internal)hard drive 205. The computing device 200 may include one or more outputdevices, such as a display 206 (e.g., an external television), and mayinclude one or more output device controllers 207, such as a videoprocessor. There may also be one or more user input devices 208, such asa remote control, keyboard, mouse, touch screen, microphone, etc. Thecomputing device 200 may also include one or more network interfaces,such as a network input/output (I/O) circuit 209 (e.g., a network card)to communicate with an external network 210. The network input/outputcircuit 209 may be a wired interface, wireless interface, or acombination of the two. In some embodiments, the network input/outputcircuit 209 may include a modem (e.g., a cable modem), and the externalnetwork 210 may include the communication links 101 discussed above, theexternal network 109, an in-home network, a provider's wireless,coaxial, fiber, or hybrid fiber/coaxial distribution system (e.g., aDOCSIS network), or any other desired network. Additionally, the devicemay include a location-detecting device, such as a global positioningsystem (GPS) microprocessor 211, which can be configured to receive andprocess global positioning signals and determine, with possibleassistance from an external server and antenna, a geographic position ofthe device.

The FIG. 2 example is a hardware configuration. Modifications may bemade to add, remove, combine, divide, etc. components of the computingdevice 200 as desired. Additionally, the components illustrated may beimplemented using basic computing devices and components, and the samecomponents (e.g., processor 201, ROM storage 202, display 206, etc.) maybe used to implement any of the other computing devices and componentsdescribed herein. For example, the various components herein may beimplemented using computing devices having components such as aprocessor executing computer-executable instructions stored on acomputer-readable medium, as illustrated in FIG. 2. Some or all of theentities described herein may be software based, and may co-exist in acommon physical platform (e.g., a requesting entity can be a separatesoftware process and program from a dependent entity, both of which maybe executed as software on a common computing device).

One or more aspects of the disclosure may be embodied in acomputer-usable data and/or computer-executable instructions, such as inone or more program modules, executed by one or more computers or otherdevices. Generally, program modules include routines, programs, objects,components, data structures, etc. that perform particular tasks orimplement particular abstract data types when executed by a processor ina computer or other data processing device. The computer executableinstructions may be stored on one or more computer readable media suchas a hard disk, optical disk, removable storage media, solid statememory, RAM, etc. As will be appreciated by one of skill in the art, thefunctionality of the program modules may be combined or distributed asdesired in various embodiments. In addition, the functionality may beembodied in whole or in part in firmware or hardware equivalents such asintegrated circuits, field programmable gate arrays (FPGA), and thelike. Particular data structures may be used to more effectivelyimplement one or more aspects of the disclosure, and such datastructures are contemplated within the scope of computer executableinstructions and computer-usable data described herein.

As mentioned above, any of the devices 110-117 may be used for receivingand/or consuming content such as, but not limited to, audio content,video content (which may or may not also include audio content), imagecontent, and/or other data. Any of the devices may be directly orindirectly in data communication with the local office 103, such as viathe links 101 and/or through one or more other wired and/or wirelessdata connections. A given data connection may be subject to variabledata connection quality over time. For instance, the available bandwidththrough a data connection may be higher or lower at different timesdepending upon factors such as signal strength, noise, shared usage ofthe data connection, availability of one or more computing resources,and the like. A lower data connection quality may potentially result in,for example, lower data transfer speeds, higher data error rates, higherdata transfer delays, and higher jitter. In general, the higher the dataconnection quality, the faster and/or more reliably may data bepotentially transferred through the data connection. And, the lower thedata connection quality, the more slowly and/or less reliably may databe potentially transferred through the data connection. However, thisdoes not necessarily need to be the result of a higher or lower dataconnection quality.

Data connection quality may be measured in any of a variety of ways. Forexample, one or more characteristics experienced by a device using thedata connection (e.g., a device receiving data over the data connectionor a device sending data over the data connection) may determine dataconnection quality based on measured bandwidth, data rate, jitter,delay, and/or error rate.

As will be described herein, historical data connection quality may beused to predict future data connection quality. Knowledge of thepredicted future data connection quality may be useful for, e.g.,determining a particular start time and/or time window for sending data.For example, if data is to be sent to a receiving device over a dataconnection, then it may, in some instances, be desirable to send thatdata during a time in which is it predicted that the data connection islikely to experience a relatively higher data connection quality ascompared with other times. To make such predictions, the system mayobtain and store information about experienced data connection qualityover a period of time. The stored information may be used to makepredictions of what the data connection quality is likely to be like ata particular future time.

FIG. 3 is a flow chart of an example method that may be performed inaccordance with one or more aspects as described herein. The methodincludes steps that may be used for, e.g., obtaining and storinginformation about data connection quality experienced by one or moredata connections. As mentioned above, the stored information may be usedto make predictions about future data connection quality. The varioussteps in this flow chart may be partially or fully performed by one ormore devices, such as by any of the elements of FIGS. 1 and 2. Whilecertain steps may be described below as being performed by a specificelement, it will be understood that this is merely an example, and thateach step may be performed by alternative elements. Moreover, while thesteps are shown in a particular order and divided into specific steps,it will be understood that the order may be modified, and that one ormore of the steps may be combined and that one or more of the steps maybe further sub-divided into further steps.

The process of FIG. 3 may run concurrently with and/or independentlyfrom the processes of FIGS. 6 and 7. At step 301, after a data sessionhas begun between a sending device and a receiving device (e.g., betweena sending computing device such as content server 106 and a receivingcomputing device such as a user device e.g., laptop computer 115), dataconnection quality information may be obtained for a current timeperiod. The time period may be a single point in time or it may be atime period having a non-zero length, such as one second, or one minute,etc. In the latter case, the determined data connection quality may be,for instance, the accumulated, average, and/or mean data connectionquality measured over the time period. The data connection qualityinformation may be obtained by, for instance, the sending device and/orthe receiving device, and/or by any other device. The data connectionquality information may include information about any one or morecharacteristics of the data connection quality, such as but not limitedto bandwidth, data rate, jitter, delay, and/or error rate. The dataconnection quality information may be obtained for different networks,e.g., networks of different providers and/or different networks of thesame provider. Each characteristic may be measured or otherwisedetermined, and may contribute to the overall data connection quality.The data connection quality information may include information abouteach characteristic and/or may include information that is a combination(e.g., hashing) of the characteristics. For example, the data connectionquality could be a single value resulting from a combination of thevarious measured characteristics.

At step 302, the obtained data connection quality information may bestored in a computer-readable medium and/or otherwise learned forimmediate and/or future use. For example, the data connection qualityinformation may be stored at the application server 107 and/or at thelaptop computer 115. Where the receiving device measures one or moreaspects of the data connection quality and the information is to bestored at the sending side of a network, the receiving device may sendinformation about the measured data connection quality to the sendingside (e.g., to the sending device). The stored data connection qualityinformation may also include or otherwise be associated with informationabout the context of the experienced data connection quality. Forexample, each measured or otherwise determined data point in the dataconnection quality information may be associated with the time of day atwhich the data connection quality is experienced, the identity (e.g.,MAC address, IP address, serial number) of the receiving device, thesoftware state of the receiving device (e.g., which Internet browser ormedia player software is being used to consume the data), the locationof the receiving device (which may be measured by, for instance, GPS orcell tower triangulation), an identification of the data being sent(e.g., a particular item of content), an identification of the Internetservice provider (ISP) and/or other service provider that may be used toprovide connectivity between the sending device and the receivingdevice, an identification of the particular data connection being usedto transfer the data, and/or an identification of a user account that isbeing used for the data transfer.

At step 303, it may be determined (e.g., by the sending or receivingdevice) whether the session has ended. If so, then the process ends forthat session. If not, then the process may return to step 301 and may berepeated to collect additional data points of the data connectionquality until the session ends. In other examples, there may not be awell-defined beginning or ending of a session, or there may be noparticular session at all. In such a case, the data connection qualityinformation may be collected intermittently (e.g., periodically)whenever the data connection is being used.

The collection of the historical data connection quality information maybe used to make predictions about future data connection quality. Thepredictions may be made using, for example, computer learning algorithmsthat are well known, such as by analyzing the information to indicateone or more patterns in the data connection quality. For example, it maybe determined using such analysis that every weekday between 5 pm and 6pm, a particular data connection experiences an increasing dataconnection quality, and that the data connection quality is generallylow between 4 pm and 5 pm on those days. Thus, it may be reasonable toexpect that, on future weekdays, the same or a similar data connectionquality pattern is likely to be experienced.

An example of such a predicted data connection quality over time isshown in the graph of FIG. 4A. In this graph, data connection quality isshown relative to time of day. While a single value is used to quantifydata connection quality in this example, in other examples there may bemultiple values/dimensions to data connection quality. For instance,there may be a first value for bandwidth, a second value for jitter, athird value for delay, and the like, all tracked over time. In somecases, a single value for data connection quality may be quantifiedbased on a combination of multiple such aspects (e.g., a combination ofbandwidth, jitter, delay, and/or any other aspects). In the presentexample of FIG. 4A, it will be assumed that the data connection qualityshown in the graph is based at least on bandwidth predicted to beexperienced by a data connection. In this example, a higher value of thedata connection quality (upward in the graph) indicates a higher/betterdata connection quality.

As shown in the example of FIG. 4A, a curve 401 represents the value ofthe predicted data connection quality versus time of day. Thus, forinstance, the data connection quality is predicted to be higher at 6 pmthan at 5 pm. The predicted values may be determined based at least onthe historical data connection quality information that may have alreadybeen collected during, e.g., the process of FIG. 3 or a similar process.

Referring to FIG. 4B, it is assumed that a particular set of data (e.g.,a particular item of content) may be requested at 5 pm to be sent to, orotherwise available to, a receiving device. The requested item ofcontent may include, for example, on-demand audio and/or video content,and may be expected to be consumed (e.g., displayed or recorded) in realtime locally by the receiving device. In this example, the item ofcontent, when consumed in real time, would last one hour (from 5 pm to 6pm). The timing of the consumption of the content by the receivingdevice is illustrated in FIG. 4B by a shaded box 402 (extending from 5pm to 6 pm). It is further noted that, in this example, it may bepredicted that there may be insufficient data connection quality from 5pm to about 5:15 pm, as indicated by a darker-shaded portion 404 of theshaded box 402. In this example, it may be determined whether thepredicted data connection quality is insufficient by comparing thepredicted data connection quality with a predetermined threshold value.If the predicted data connection quality is less than (or less than orequal to) the threshold value, then it may be determined that thepredicted data connection quality is insufficient. If the predicted dataconnection quality is greater than (or greater than or equal to) thethreshold value, then it may be determined that the predicted dataconnection quality is sufficient to send the requested data in a mannerso as to be successfully consumed in real time.

One solution for addressing insufficient predicted data connectionquality may be to reduce the quality of the data being sent. Forexample, where the requested data is an item of audio and/or videocontent, the audio and/or video may be reduced in quality (e.g., byreducing resolution and/or frame rate, and/or by increasing datacompression). However, depending upon how low the data connectionquality is, this may or may not be acceptable to the user of thereceiving device.

Another solution may be to send at least a portion of the requested databefore it is actually requested by the user. To accomplish this, it maybe desirable to not only predict future data connection quality, butalso to predict future requests for data (e.g., future requests foritems of content such as on-demand audio and/or video content). This maybe done by, for example, collecting information about past requests fordata or other content, and using these past requests to make predictionsof future requests. Thus, in the process of FIG. 3, for example,information about a request for content or other data for a givensession (or even in a session-less environment) may be recorded alongwith the information about data connection quality. The requestinformation may also be correlated with time. Like the historical dataconnection quality information, the set of data points of historicalrequests may also be correlated with other factors as mentioned above,such as the identity (e.g., MAC address, IP address, serial number) ofthe device from which the request is received and/or of the devicereceiving the requested content, the software state of the device (e.g.,which Internet browser or media player software is being used to consumethe data), the location of the requesting and/or receiving device (whichmay be measured by, for instance, GPS or cell tower triangulation), anidentification of the data being sent (e.g., a particular item ofcontent), an identification of the Internet service provider (ISP)and/or other service provider that may be used to provide connectivitybetween the sending device and the requesting and/or receiving device,an identification of the particular data connection being used totransfer the data, and/or an identification of a user account that isbeing used for the request and/or the data transfer.

Predictions of future requests may be made using, for example,computer-implemented learning algorithms. For example, if a particularuser has typically requested an on-demand viewing of the most recentepisode of a particular television series at or around 5 pm onThursdays, then it may be predicted that the user will likely againrequest the most recent episode at approximately 5 pm on a futureThursday. Moreover, if the request is typically to view the episode on aparticular device of the user, then it may further be predicted that theuser will again request to view the episode in the future on thatparticular device.

By using both the historical data connection quality and requestinformation, the system may be able to make predictions as to what islikely to be requested in the future and when it is likely to berequested, and correlate such predicted requests with predicted futuredata connection quality to determine how to appropriately deliver therequested content or other data. Referring again to the example of FIG.4B, it is predicted that the user will request a one-hour long item ofon-demand content at 5 pm (as indicated by box 402). It is furtherpredicted that, from about 5 pm to about 5:15 pm, data connectionquality may be relatively low, for instance, below a predeterminedthreshold value as indicated by line 403. In this example, because thedata connection quality may be so poor for the first fifteen minutes ofthe content (when consumed in real time), it may be desirable topre-deliver at least the first fifteen minutes (or other portion) of thecontent, even before a request for the content is made by the user.

An example of such pre-delivery is shown in FIG. 4C. In this example, aportion of the content, indicated by box 405, is pre-delivered to thereceiving device before a request for the content is received from theuser or from the receiving device. Because the data connection qualitymay be relatively poor in this example during pre-delivery, thepre-delivered content portion 405 may take longer than it would take toconsume the content in real time. In this way, a better quality versionof the content portion 405 may be pre-delivered. Thus, in this example,although the content portion 405 represents the initial fifteen minutesof the content 402 when consumed in real time, the pre-delivery of thecontent portion 405 may take longer, such as about one hour in thisexample.

It can also be seen in FIG. 4C that the latter portion of the content402 (in this example, beginning fifteen minutes of real-time consumptioninto the content 402), may not be delivered until it is needed in realtime during consumption. Thus, a first portion of the content (portion404/405) may be pre-delivered to the receiving device prior to a requestfor the content, and a second portion of the content (e.g., theremainder) may be sent to the receiving device in response to thecontent and when needed. In this example, since the receiving device mayconsume the initial portion 404/405 of the content from local datastorage device of the receiving device, the remainder of the content 402may be sent (e.g., streamed) to the receiving device only upon thelocally-stored portion being fully consumed (or nearly so, such asconsumed by at least a threshold amount such as 95% of thelocally-stored content). When the threshold amount is consumed, then thereceiving device may send a request upstream to the sending device torequest further sending of the remaining content, such as by streaming.

In other examples, the first portion of the content (portion 404/405)may be pre-delivered to a destination other than the receiving device.For example, the first portion of the content may be pre-delivered to aserver or other computing device associated with the receiving device,such as a media server on the same local network as the receivingdevice, or to some other local-area storage device such as a local-areastorage device of a cellular network base station, etc. For instance, aparticular user may take the 8:30 train into the city for work eachweekday. While the train stations at either end may be covered byhigh-capacity operator WiFi, the uplinks from these train stations tolarger core networks may be more constrained. Otherwise, the user'sdevice may be reachable by, e.g., a cellular 3G/4G mobile data network.In this case, it may be desirable to pre-deliver (e.g., push and/orinstruct the device to pull) content to the device and/or toward thedevice to another destination, depending upon what is desired, whichmeans of connectivity is most available, and/or other factors. Anexample of such a destination other than the device may be a local-areastorage device or system associated with the train station. Then, thelocal-area storage device or system may deliver the first portion of thecontent and/or any other portions of the content to (e.g., push to ormake available to) the user device. In this example, by the networkpre-delivering content toward, but not necessarily all the way to, thereceiving device, this may allow conservation of the bandwidth of themore constrained uplinks and/or allow, e.g., full burst transfer whilein range of the high-capacity WiFi. Thus, while various examples hereinrefer to sending or pre-delivering content to the receiving device,these examples may also be implemented such that the content is sent orpre-delivered to another destination. In these cases, the content maysimultaneously and/or later be transferred from the other destination tothe receiving device.

In the example of FIG. 4C, the initial portion 405 takes longer topre-deliver than it would to consume in real time (e.g., one hour versusfifteen minutes). This is because, in this example, the data connectionquality is lower than would be needed for real-time streaming of thecontent at the desired content quality level. However, in otherexamples, the data connection quality may be higher during pre-deliverysuch that the initial portion 405 of the content may be delivered atreal-time consumption speed or even faster than real-time consumptionspeed. In fact, the system may schedule pre-delivery at a particulartime to correspond to a desired level of data connection quality. Forexample, if the data connection quality in FIG. 4C is much higher from 1pm to 2 pm (not shown in the graph), then pre-delivery may be scheduledto occur at a time between 1 pm and 2 pm to potentially reduce therelative amount of transfer time. The scheduled time of pre-delivery mayalso be determined based on other factors, such as availability of thereceiving device, time-of-day cost for delivering data such as inaccordance with an agreement with the user's ISP (e.g., certain peaktimes may be more expensive than others for data delivery), usage of thedata connection, etc. In further examples, the sending of the initialportion 405 may at least partially overlap in time with (e.g., be sentat least partially concurrently with) the remainder of the item ofcontent 402.

In the examples of FIGS. 4A-4C, an initial portion of content waspre-delivered before the content was requested. In further examples, itmay be that a portion of content may be pre-delivered before it is to beconsumed, however the pre-delivery may at least partially occur afterthe content is requested. For example, referring to FIG. 5A, the curve501 represents an example of various values of predicted data connectionquality over time. At FIG. 5B, it can be seen that an item of content502 is requested and begins streaming to the receiving device at 5 pm.In this case, the predicted data connection quality is greater than thepredetermined threshold 403 from about 5 pm to about 5:30 pm, andtherefore it may be desirable to simply send in real time (e.g., stream)or faster the requested content beginning at 5 pm. At 5:30 pm, it ispredicted in this example that the data connection quality is to dropbelow the predetermined threshold 403. Therefore, it is likely, based onthe prediction, that a latter portion (represented by box 505) of thecontent, beginning at about 5:30 pm, is likely to be of degraded qualityor even fail to send at all.

It may therefore be desirable to pre-deliver the latter portion of thecontent before it is to be consumed, and store the pre-delivered portionin local storage at the receiving device. This may be similar topre-delivery as in FIG. 4C, except in the example of FIG. 5C, thepre-delivery may occur at least partially after the content is requestedand/or after an initial portion of the content has begun being sent to(e.g., streamed to) the receiving device. This may also mean that thelatter portion 505 may be sent at least partially simultaneously withthe initial portion of the content. This is shown in FIG. 5C, in whichthe latter portion 505 of the content overlaps in time with the graphwith the earlier portion of the content 502. To send the two portions ofthe content to the receiving device at least partially simultaneously,the two portions may be sent, for example, using different channelsand/or streams. In this case, the receiving device may tune to bothchannels and/or streams simultaneously, and switch/transition betweenwhich portion of content to display to the user at the appropriate time.In some cases, the transition may be performed seamlessly such that thetransition between the streamed content portion and the storedpre-delivered content portion may be smooth and/or undetectable by thehuman eye.

FIG. 6 is a flow chart of an example method that may be performed inaccordance with one or more aspects as described herein. The methodincludes steps that may be used for, e.g., scheduling and/or otherwiseinitiating pre-delivery of as-yet unrequested content using predictedand/or measured data connection quality information. The various stepsin this flow chart may be partially or fully performed by one or moredevices, such as by any of the elements of FIGS. 1 and 2. While certainsteps may be described below as being performed by a specific element,it will be understood that this is merely an example, and that each stepmay be performed by alternative elements. Moreover, while the steps areshown in a particular order and divided into specific steps, it will beunderstood that the order may be modified, and that one or more of thesteps may be combined and that one or more of the steps may be furthersub-divided into further steps.

The process of FIG. 6 may run concurrently with and/or independentlyfrom the processes of FIGS. 3 and 7. At step 601, the accumulatedhistorical content requests for one or more users and/or receivingdevices may be analyzed, such as for patterns. As discussed above, theanalysis may be performed using, for example, a machine learningalgorithm and/or using statistical analysis. For instance, Table 1 belowshows an example of content request history for a particular user thatmay be stored and used for analysis. Such information may exist for eachuser and/or for each receiving device. From such a history, it may bedetermined, for instance, that a particular user and/or receiving devicemay historically request, on an on-demand basis, the most recent episodeof an ongoing television series, and that the requests may be made, forexample during a particular timeframe (e.g., particular time of day orwindow of time), and/or on particular days of the week. For instance,referring to Table 1, there may be a pattern where sequential episodesof a particular item of content, referred to herein generically asContent A, are requested at generally the same time of day on the sameday of the week. The analysis of step 601 may be performed by, forexample, the application server 107, the receiving device, (e.g., any ofelements 110-117), and/or any other one or more computing devices.

TABLE 1 Receiving Device Timestamp Content device 1 5/1/2000, 5:03:17 pmContent A, episode 4 device 1 5/8/2000, 5:07:02 pm Content A, episode 5device 2 5/9/2000, 9:43:14 am Content B device 1 5/10/2000, 9:13:48 pmContent C device 3 5/12/2000, 11:35:16 pm Content D device 1 5/15/2000,4:59:28 pm Content A, episode 6

At step 602, using the outcome of the analysis of historical contentrequests, future content requests may be predicted. For example, wherethe particular user and/or receiving device historically requests, on anon-demand basis, the most recent episode of an ongoing televisionseries, it may be predicted that this pattern of requests is likely tocontinue in the future. Referring to the example of Table 1, it may bepredicted that it is likely, based on historical content requestpatterns, that the user will request, on May 22, 2000, at approximately5 pm, that Content A, episode 7, be sent to device 1. While there is noguarantee that the prediction is correct, it may be determined to be alikely future request based on the historical requests. The predictionof step 602 may be performed for future predicted requests during asliding future time window. The time window may or may not include thepresent time, and may be of a fixed or variable length of time. Forexample, the prediction of step 602 may be made for any predictedrequests occurring within the next hour, or within the next four hours,or within the next day, or within the next week, or “this week,” or“today.” The start of the time window may be the present time (the timeat which the prediction is being made) or it may start at a future time.For example, the time window may be “tomorrow” or “next week.”

At step 603, for each of the predicted future content requests, it maybe determined whether any pre-delivery of the requested content shouldbe scheduled. To determine this, the predicted timeframe of when thecontent would be sent in response to the future request may becorrelated with the predicted data connection quality at that timeframe.For example, it may be predicted that Content A, episode 7, will likelybe requested at a 5 pm, and that the episode is scheduled to play forone hour. Therefore, the predicted likely potential timeframe for thecontent to be sent might be between 5 pm and 6 pm. This timeframe may becompared with the predicted data connection quality and determinedwhether there may likely be a problem with sending the content duringthat timeframe. For example, the predicted data connection qualityduring that timeframe may be compared with a predetermined threshold(e.g., the threshold 403). For any portions of the timeframe in whichthe predicted data connection quality is below (or equal to or below)the threshold, then it may be determined that at least that portion ofthe content likely to be playing at that time should be pre-delivered.

For example, referring again to FIG. 4B, it can be seen that thepredicted data connection quality 401 is lower than the threshold 403between 5 pm and 5:15 pm, but not for the remainder of the timeframe.Therefore, it may be determined that the portion of the content thatwould be predicted to be played between 5 pm and 5:15 pm may bepre-delivered, as shown by box 405 in FIG. 4C. Referring to the exampleof FIG. 5B, it can be seen that the predicted data connection quality401 is lower than the threshold 403 between 5:30 pm and 6 pm, but notfor the remainder of the timeframe. Therefore, it may be determined thatthe portion of the content that would be predicted to be played between5:30 pm and 6:00 pm may be pre-delivered, as shown by box 505 in FIG.5C. In the example of FIG. 5C, the pre-delivery is performedsimultaneously with the streaming of the initial portion of the content502. However, pre-delivery of the latter content portion 505 may beperformed prior to any request for the content 502. It is also notedthat pre-delivery may be performed for any one or more portions of anitem of content, even a middle portion, and is not just limited topre-delivery of a beginning portion and/or an end portion.

In addition to determining whether any item of content or portionthereof is to be pre-delivered prior to a predicted future request forthe item of content, step 603 may also include determining how far inthe future (e.g., determine a scheduled start time or timeframe) topre-deliver the item of content or portion thereof. In general, the itemof content or portion thereof may begin being pre-delivered (e.g.,downloaded, streamed, or otherwise sent) to the receiving device anamount of time T before the predicted request for the item of content tobe sent to the receiving device. The amount of time T may be determinedin any of a variety of ways. For example, the value of T may be apredetermined fixed amount of time (e.g., one hour, or two hours, ortwelve hours, or one day). Or, the value of T may depend at least uponthe amount of data to be pre-delivered, where a larger amount of datamay result in a larger value of T, and a smaller amount of data mayresult in a smaller value of T. In addition or alternatively, the valueof T may depend at least upon the predicted future data connectionquality at a timeframe prior to the predicted request for the item ofcontent. For instance, if the predicted data connection quality is to bebetter (e.g., higher), then the value of T may be lower than if thepredicted data connection quality is to be worse (e.g., lower). This isbecause a better data connection quality may be expected to allow for ahigher data transfer rate (e.g., a higher available bandwidth) ascompared with a worse data connection quality. For example, if thepredicted data connection quality for the timeframe two hours before apredicted request is relatively poor, then T may be set to two hours(e.g., the pre-delivery may begin two hours before the predicted requestfor the item of content). If, on the other hand, the predicted dataconnection quality for that same two-hour timeframe is relatively good,then T may be set to a smaller value, such as one hour, before thepredicted request for the item of content (e.g., the pre-delivery maybegin one hour before the predicted request for the item of content).Another factor that may affect the value of T may include, for example,which other data is scheduled to be pre-delivered during the timeframe.If, for instance, several other items of content (or portions thereof)are already scheduled for pre-delivery to the receiving device and/or toother receiving devices in that same timeframe, then the pre-delivery ofone or more of those items of content may be scheduled so as to not alloccur at the same time and/or in an overlapping manner (thereby reducingthe amount of bandwidth needed for pre-delivery).

At step 604, the content (or portion thereof) is pre-delivered to theappropriate one or more receiving devices at the scheduled time(s). Theprocess of steps 601-604 may be repeated as often as desired, such as ona periodic (e.g., hourly, daily, or weekly) basis, and/or in response toupdates to the historical data connection quality information and/or tothe historical content request information.

FIG. 7 is a flow chart of an example method that may be performed inaccordance with one or more aspects as described herein. The methodincludes steps that may be used for, e.g., providing content and/orother data to a receiving device. The various steps in this flow chartmay be partially or fully performed by one or more devices, such as byany of the elements of FIGS. 1 and 2. While certain steps may bedescribed below as being performed by a specific element, it will beunderstood that this is merely an example, and that each step may beperformed by alternative elements. Moreover, while the steps are shownin a particular order and divided into specific steps, it will beunderstood that the order may be modified, and that one or more of thesteps may be combined and that one or more of the steps may be furthersub-divided into further steps.

The process of FIG. 7 may run concurrently with and/or independentlyfrom the processes of FIGS. 3 and 6, and may be triggered in response toa request for an item of content to be provided to a receiving device.Accordingly, at step 701, a device in the network (for example, theapplication server 107) may receive a request by the receiving device,through the network, for an item of content to be consumed (e.g.,displayed, downloaded, and/or recorded) on demand. The request mayinvolve, for example, sending a data message upstream through thenetwork by the receiving device and/or by another device. In otherexamples, the request may be transmitted through a different networkthan the network over which the item of content is to be sent to thereceiving device.

At step 702, the receiving device and/or the application server 107 (forexample) may determine whether an initial portion (e.g., a portion thatincludes the beginning of the requested item of content, such as theportion indicated in FIG. 4C by block 405) is already locally stored atthe receiving device. In other words, it is determined whether theinitial portion has already been pre-delivered prior to the request. Asdiscussed above, pre-delivery may occur based on a prediction that therequest is going to occur.

If the initial portion is already locally stored, then the process maymove to step 703, and the pre-delivered initial portion of the requestedcontent may begin playing (e.g., being displayed to the user of thereceiving device) from the local storage of the receiving device. Atstep 704, the receiving device, the application server 107, and/oranother device may also determine (e.g., measure) the actual dataconnection quality currently experienced by the receiving device, andthis information may be shared with, e.g., the application server 107and/or the receiving device as appropriate.

If the initial portion is not already locally stored, then at step 705,the actual data connection quality currently experienced by thereceiving device may be determined (e.g., measured), such as by theapplication server 107, the receiving device, and/or another device.Again, this data connection quality information may be shared asappropriate. At step 706, the requested item of content may begin beingsent (e.g., streamed) downstream over the network to the receivingdevice. The content being sent at step 706 may be formatted in a mannerappropriate for the current data connection quality. For instance, ifthe current data connection quality is relatively poor, then the contentmay be provided at a relatively low quality, such as at a low bit rate,low frame rate, and/or using high data compression, etc. On the otherhand, if the current data connection quality is relatively good, thenthe content may be provided at a relatively higher quality, such as at ahigher bit rate, higher frame rate, and/or using less data compression,etc.

Both branches of the process from steps 704 and 706 may then move tostep 707, in which the receiving device, the application server 107,and/or another device may determine whether the actual current dataconnection quality (as determined at step 705 or step 703) is consistentwith the predicted data connection quality for the current timeframe.Consistency between the predicted and actual values may be evaluated inany of a variety of ways. For example, it may be determined that the twovalues (predicted and actual) are consistent with each other if they arewithin a predetermined threshold difference (e.g., absolute differenceor percentage difference) from each other. For example, if the twovalues are within 5% of each other, or within 10% of each other, orwithin 25% of each other, then the two values may be considerconsistent, meaning that the predicted data connection quality turnedout to be sufficiently accurate. If the two values are inconsistent,then this may mean that the predicted data connection quality turned outto be relatively inaccurate.

If the current (e.g., measured) actual data connection quality isconsistent with the predicted data connection quality, then the processmay move to step 709, in which predicted data connection quality (basedon the historical data connection quality values collected in steps 301and 302) may continue to be used for predicting whether futurepre-loading of any portion of the item of content is appropriate.However, if the current (e.g., measured) actual data connection qualityis inconsistent with the predicted data connection quality, then theprocess may move to step 708, in which predicted data connection qualitymay be considered unreliable at this time, and so the actual currentdata connection quality may be used for predicting whether futurepre-loading of any portion of the item of content is appropriate duringcontent playback. In the above example, only the predicted values (basedon historical data connection quality values) may be used (step 709), oronly the current measured data connection quality may be used (step708), depending upon the consistency between the two values. However, inother examples, a combination of the two (prediction based on historicalvalues, and current actual value) may be used to predict the future dataconnection quality during the remainder of the content playback.

Both branches of the process at steps 708 and 709 may then move to step710, in which the receiving device, the application server 107, and/oranother device may determine, based on the prediction as made in step708 or step 709, whether to pre-load any upcoming portion of the item ofcontent. For example, if it is predicted that the data connectionquality will be relatively poor (e.g., lower than a predeterminedthreshold value), then it may be determined that pre-loading isappropriate. If it is predicted that the data connection quality will berelatively good (e.g., higher than a predetermined threshold value),then it may be determined that pre-loading is not appropriate. If thedetermination is that pre-loading is appropriate, then such pre-loadingis performed in step 711. Otherwise, step 711 is skipped. An example ofsuch pre-loading of an upcoming portion of content, while the content iscurrently being played back, is shown in FIG. 5C, in which thepre-loaded upcoming portion is represented by block 505. As previouslydiscussed, the pre-loading of the upcoming portion of the content may beperformed concurrently with the sending (e.g., streaming) of thecurrently-played-back content (represented by block 502). Thepre-loading of the upcoming portion of the content may be sent to thereceiving device on, for instance, a separate channel and/or separatestream from the channel and/or stream containing thecurrently-played-back content.

The process may then move to step 712, in which the receiving device,the application server 107, and/or another device may determine whetherit is appropriate to switch the playback of the content (e.g., thedisplayed content) between the locally-stored pre-loaded version and thelive-sent (e.g., streamed) version. For instance, if the locally-storedpre-loaded portion is currently being displayed to the user (as may beinitiated, for example, at step 703), and if that locally-stored portionis ending, then the display of content may switch over to displaying thelive-streamed version of the content. This switching may be done in aseamless manner (e.g., undetectable to the human senses), if desired.Or, for instance, if the live-streamed content is currently beingdisplayed to the user (as may be initiated, for example, at step 706),and if there exists a locally-stored portion that begins at a currentplayback point in the streamed content, then the display of content mayswitch over to displaying the locally-stored version of the content.Again, this switchover may be seamless if desired.

The process may then move back to step 704 to again determine (e.g.,measure) the current data connection quality, and the process may repeatas many times as desired. For instance, the process may repeat until theitem of content ends or is otherwise terminated. In that case, theprocess of FIG. 7 may end and may begin again upon another request forcontent being initiated at step 701.

Although example embodiments are described above, the various featuresand steps may be combined, divided, omitted, and/or augmented in anydesired manner, depending on the specific outcome and/or application.Various alterations, modifications, and improvements will readily occurto those skilled in art. Such alterations, modifications, andimprovements as are made obvious by this disclosure are intended to bepart of this description though not expressly stated herein, and areintended to be within the spirit and scope of the disclosure.Accordingly, the foregoing description is by way of example only, andnot limiting. This patent is limited only as defined in the followingclaims and equivalents thereto.

What is claimed is:
 1. A method, comprising: determining, by at leastone computing device, prior to receiving a request for an item ofcontent, a future point in time based at least on information indicatinga correlation between a past timeframe and data connection quality; andsending, prior to the request, at least a first portion of the item ofcontent beginning at the determined future point in time.
 2. The methodof claim 1, wherein the item of content comprises video data.
 3. Themethod of claim 1, wherein the information comprises information aboutdata connection quality previously experienced between a device and thenetwork.
 4. The method of claim 1, further comprising: receiving therequest from a device for the item of content; and streaming, throughthe network, a second portion of the item of content to the device inresponse to the request.
 5. The method of claim 1, wherein the methodfurther comprises determining the item of content based on previousrequests for other items of content.
 6. The method of claim 1, whereinsaid determining the future point in time comprises determining thefuture point in time also based on previous requests for other items ofcontent.
 7. The method of claim 1, further comprising: generating theinformation by determining, for each of a plurality of time periodsoccurring before said future point in time, a data connection qualityexperienced during the respective one of the time periods.
 8. The methodof claim 1, wherein said sending comprises sending, prior to therequest, at least the first portion of the item of content beginning atthe determined future point in time.
 9. A method, comprising:predicting, by at least one computing device, based at least onhistorical data connection quality, a future data connection quality;determining, by the at least one computing device, based at least on thepredicted future data connection quality, whether to pre-deliver atleast a portion of an item of content; and if so, then pre-deliveringthe at least the portion of the item of content.
 10. The method of claim9, further comprising: determining the historical data connectionquality by determining, for each of a plurality of time periodsoccurring before said predicting, a data connection quality experiencedby the device during the respective one of the time periods.
 11. Themethod of claim 9, wherein said pre-delivering is initiated before theitem of content is requested by the device, and wherein saidpre-delivering comprises pre-delivering the at least the first portionof the item of content to the device.
 12. The method of claim 11,wherein the at least the portion is a first portion of the item ofcontent, and wherein the method further comprises: receiving a requestby the device for the item of content; and streaming, through thenetwork, a second portion of the item of content to the device inresponse to the request.
 13. The method of claim 9, further comprisingdetermining a time to pre-deliver the at least the portion of the itemof content based at least on the historical data connection quality,wherein said pre-delivering comprises pre-delivering the at least theportion of the item of content at the determined time.
 14. A method,comprising: predicting, by at least one computing device, a dataconnection quality based at least on historical data connection quality;determining, by the at least one computing device, whether a currentdata connection quality is consistent with the predicted data connectionquality; determining, by the at least one computing device, whether tosend at least a portion of an item of content using: the predicted dataconnection quality if the current data connection quality is consistentwith the predicted data connection quality, and the current dataconnection quality if the current data connection quality isinconsistent with the predicted data connection quality; and if so, thensending the at least the portion of the item of content.
 15. The methodof claim 14, where said determining whether the current data connectionquality is consistent with the predicted data connection qualitycomprises determining whether a difference between the current dataconnection quality and the predicted data connection quality is within apredetermined threshold value, and if so, then determining that thecurrent data connection quality is consistent with the predicted dataconnection quality.
 16. The method of claim 14, wherein said sendingcomprises sending the at least the portion of the item of content to thedevice before the item of content is requested by the device.
 17. Themethod of claim 14, wherein the current data connection qualitycomprises a current available bandwidth between the device and anetwork, and wherein said sending comprises sending the at least theportion of the item of content to the device through the network. 18.The method of claim 14, wherein the at least the portion is a firstportion of the item of content, and wherein the method further comprisessending a second portion of the item of content to the device inresponse to a request by the device for the item of content.
 19. Themethod of claim 14, further comprising determining the at least theportion of the item of content based on at least one of the predicteddata connection quality and the current data connection quality.
 20. Themethod of claim 14, further comprising: determining, by the device, thecurrent data connection quality; and indicating, by the device, to theat least one computing device, the current data connection quality.